Plan Copy

The OIRW application introduces a new Plan Copy option under the Tools main menu. This utility allows authorised users to create a new plan by duplicating an existing plan’s configuration, including associated business rules, transactions, segments, and related setup components. This helps users replicate plan structures across different company, subsidiary company, or product hierarchies without rebuilding the setup manually.

The Plan Copy utility can only be used in development mode. When a plan is copied, valuation settings are not transformed or modified during the copy process.

The utility creates a copy of the selected plan along with all associated records. Users may either copy the complete configuration or selectively choose specific business rules, transactions, segments, funds, and related plan components.

All copied business rules, transactions, and segment names are automatically versioned and created as Version 1 in the target environment.

If the plan is copied within the same environment, the system automatically generates new GUIDs for the copied plan and associated entities.

The Plan Copy utility also provides flexibility by allowing users to either copy the complete plan configuration or selectively include specific rules and components during the copy process. This enables efficient reuse of existing plan setups across environments and organisational structures while supporting customisation based on business requirements.

A copied plan has to be renamed to distinguish it from the original plan. The utility creates a copy of the plan and all associated records. Users may choose to copy all rules or selectively include only specific rules. When copying within the same environment, the system generates new GUIDs for the copied plan. Effective and expiration dates can also be modified, allowing users to create a new plan based on an existing one with updated timelines.

All copied business rules, transactions, and segment names are versioned automatically and begin as Version 1 in the target environment.

Once the source and target environments are selected, the system displays a list of plans available for copying from the source environment. Users then select the level to which the plan should be copied in the target environment:

  • Company

  • Subsidiary Company

  • Product

The source and target levels must always match. New levels cannot be created during the plan copy process and must already exist in the target environment before the copy operation begins.

Before the copy process begins, the system validates that the required hierarchy levels already exist in the target environment.

New company, subsidiary company, or product levels cannot be created during the plan copy operation and must be configured beforehand in the target environment.

Note: The level of the plan must remain the same in both the source and target environments. For example:
- A primary company-level plan can only be copied to a primary company-level in the target environment.
- A subsidiary company-level plan can only be copied to a subsidiary company-level in the target environment.
- A product-level plan can only be copied to a product level in the target environment.

Products

  • If products are enabled in the source environment but disabled in the target environment (or vice versa), the plan copy process cannot proceed beyond the first screen. The system displays a validation error message preventing the user from continuing until the source and target product configurations are aligned.

  • If products are enabled in both environments, all plans must belong to a product group as per the current application functionality.

  • If a user wants to copy a plan associated with a product in the source environment, but the product does not exist in the target environment, the following two-step process must be followed:

    • Create the new product in the target environment using the Plan Copy utility.

    • Copy the plan into the newly created product in the target environment.

This process ensures that the product and plan hierarchy remain aligned between the source and target environments. A plan that exists in one Product in the source environment may also be copied into a different Product in the target environment.

Note: Additional setup activities must be completed in the target environment after the Plan Copy process finishes in order to activate and process the copied plan successfully. These activities include updating:
- Rule security (transaction security)
- Translations
- Administration table entries
- Missing global rules
- Screen rules
- Segment Calculate General rules
- Sequence table updates

The system displays all configured target environments that have IVS enabled and are linked to the same IVS as the source environment.

Security Privilege

Only users assigned to a security role with the required privilege can access the Plan Copy option. To support this functionality, a new privilege is introduced in the IVSPRIVILEGE entity with the following details:

PRIVILEGENAME Utilities-PlanCopy
Description Allow access to Plan Copy Tool

Prerequisite: To access the Plan Copy option, a user must be assigned to a security role that possesses the Utilities-PlanCopy privilege. If the user lacks this privilege, the system prevents the plan copy operation and displays an authorisation error.

Plan Copy Workflow

  • Log in to the Oracle Insurance Rules Workbench using valid credentials.

  • Select the target environment.

  • When the user selects the target environment, the system prompts for the target environment database credentials before continuing with the wizard.

  • Select the source plan to copy.

  • The source environment is the environment in which the user is currently logged in when the Plan Copy utility is launched.

  • Navigate to the Tools menu from the top-right corner and select Plan Copy.

Clicking the Plan Copy option displays a guided step-by-step workflow along with the configured target environments. If no additional environments are configured, the initially selected environment is displayed by default.

Plan Properties

  • Select the target environment to enable source plan selection.

  • The system displays the plan properties screen, where all required inputs must be updated.

  • Only environments configured with the same IVS as the source environment are available for selection as valid target environments.

Source Properties

The system displays options to select either of the following:

  • Primary Company, or

  • Subsidiary Company

If the user selects the primary company as the source:

  • The system disables the Product field.

  • The system enables only the Plan dropdown.

  • The system lists plans available under the selected primary company.

  • In the Target section, the system displays Primary Companies in the Target Parent field.

If the user selects the subsidiary company as the source:

  • The system enables the Product field.

  • The system enables the Plan dropdown with plans available under the selected Product.

  • In the Target section, the system displays available products in the Target Parent field.

The system lists companies from the source environment and all primary companies configured in the target environment.

After the user selects a company:

  • The Product field becomes enabled only if the selected company contains corresponding products.

  • The user selects a product available under the selected subsidiary company.

  • The system enables the Plan field.

  • The user selects the required plan from the available list.

Target Properties

Under Target Properties:

  • The user selects the target parent based on the source selection (primary company or product).

  • The system lists all products configured under the target environment.

  • The user enters:

    • New Plan Name

    • Effective Date

    • Expiration Date

  • By default, the New Plan Name field is populated with the source plan name.

  • The user may modify the plan name if required.

  • If a plan with the same name already exists in the target environment, the system displays the following validation error: “A plan already exists in the target, please enter a new plan name.”

Preserve GUIDs and Copy All Rules

Preserve GUIDs

This option is available only when the source and target environments are different.

When the user selects Preserve GUIDs:

  • The system auto-populates the Plan Name field with the source plan name.

  • The Plan Name field becomes disabled.

  • The following GUIDs are preserved:

    • PlanGUIDs

    • BusinessRuleGUIDs

    • TransactionGUIDs

    • SegmentNameGUIDs

Conditional Behaviour:

  • If the source and target environments are the same, the system disables the Preserve GUIDs option.

  • If Preserve GUIDs is selected, the existing plan name is retained automatically.

Copy All Rules

If the user selects Copy All Rules:

  • The system skips directly to the Release Management step.

If this option is not selected:

  • The system guides the user through the rule selection process.

Selective Copy Options

If Copy All Rules is not selected, the wizard navigates through additional configuration selection screens where users may selectively include:

  • Business Rules

  • Transactions

  • Segments

  • Plan Funds

  • Plan Model Definitions

  • Plan Program Definitions

  • Segment Program Definitions

  • Comment Templates

  • Activity Filters

  • Requirements

  • Additional Plan Data

Additional plan data includes:

  • Plan Allocations

  • Plan Withholding

  • Plan and Segment State Approvals

Rule Selection

The system navigates to the list of rules page where the required rules can be selected.

Next, the Rule Details page displays:

  • Available Rules

  • Assigned Rules

Users can move rules between sections using the arrow controls and then click Next. During the copy process, the system validates whether global rules already exist in the target environment to prevent duplicate rule creation.

Important:
- Fund Selection Rules: During fund selection, a child fund or benefit fund cannot be copied unless the corresponding parent fund is also selected. If a parent fund contains multiple child or benefit funds, users may select any required combination of child funds while leaving others unselected.
- MarketMaker Information: MarketMaker information is automatically copied when a valid MarketMakerGUID exists at the plan level.The MarketMakerGUID must not be null in the AsPlan table for the selected source plan.

Release Management

Release management functionality is available only when enabled in the target environment.

The workflow then navigates to the release management page where users can either

  • Add a new configuration package, or

  • Select an existing configuration package from the available list.

If Release Management is enabled, the copied plan can be added to a configuration package. Once deployed, the configuration package allows the copied plan to be migrated across multiple environments without repeating the plan copy process.

Review and Completion

The final step displays the Review and Complete page summarising the following:

  • Applied rules

  • Assigned privileges

  • Package details

The navigation tree displays all copied plan components

If changes are required, users must navigate back to the appropriate wizard step and update the configuration before completing the process.

Users can verify the details and click the following:

  • Finish to proceed with the plan copy process, or

  • Cancel to abort the operation.

Clicking Finish displays a confirmation dialogue box.

After confirmation, the system displays a success message indicating that the plan copy request has been submitted successfully.

If the plan is copied into the same environment as the source environment, users must log out and log back into the application before the copied plan becomes visible in the navigation tree.